Advanced memory management architecture for large data volumes

ABSTRACT

An efficient memory management method for handling large data volumes, comprising a memory management interface between a plurality of applications and a physical memory, determining a priority list of buffers accessed by the plurality of applications, providing efficient disk paging based on the priority list, ensuring sufficient physical memory is available, sharing managed data buffers among a plurality of applications, mapping and unmapping data buffers in virtual memory efficiently to overcome the limits of virtual address space.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The present invention relates to data processing, and more particularlyto a virtual memory management system and method for handling large datavolumes.

2. Discussion of the Related Art

Applications for visualizing three-dimensional volume data utilizememory intensive methods such as ray-casting, splatting, and shear-warp.The volume data visualized by these methods can be obtained from medicaltomographic scanners such as Magnetic Resonance (MR), ComputedTomography (CT), Positron Emission Tomography (PET), or any otherapparatus capable of producing a series of slices in a grid-like array.Many volume visualization methods are implemented using a programmedcomputer, and rely on the computer's virtual memory and virtual pagingsystem for storing and accessing slice data. Personal computersavailable today typically use operating systems such as Windows NT,Windows XP, Unix, or Linux. Such operating systems employ methods ofvirtual memory addressing and virtual paging. The performance of virtualmemory addressing and virtual paging in a programmed computer decreasesconsiderably when memory is allocated for a very large number of slicesof a large three-dimensional volume and the total memory allocated islarger than the available Random-Access Memory (RAM) of the programmedcomputer, also known as physical memory. Such a decrease in theperformance of virtual memory addressing and virtual paging also causesa substantial decrease in the performance of volume visualizationmethods.

Memory limitation have been exacerbated by recent technological advancesin the field of tomographic imaging, which have improved the spatialresolution and speed of data acquisition, resulting in the production ofvery large datasets comprising hundreds, and even thousands of slices.For example, it is possible to rapidly generate a sequence of 1024slices using the Siemens SOMATOM VolumeZoom™ CT scanner, with each slicecomprising a grid of 512×512 picture elements, resulting in athree-dimensional volume of 512×512×1024 volume elements (over 268million data values). In the Oil and Gas industry, seismic datameasurements are also stored in very large three-dimensional volumes,with as many as 2048×2048×2048 grid elements (over 8.5 billion datavalues). These types of data can be larger than the Random-Access Memory(RAM) storage available on modern computers. Some three-dimensionalarrays can be so large that their size exceeds the memory addressingcapability of 32-bit Central Processing Units (CPU) found in manypersonal computers and graphic workstations, which is typically limitedto a maximum of 4.2 billion data elements.

One limitation of conventional virtual paging methods available in theart is that they are designed to be general-purpose, and theirperformance is not optimized for handling a large number of slices of athree-dimensional volume efficiently. When the Random-Access Memory of acomputer becomes overloaded with too many slice buffers, the probabilitythat the virtual paging system will page out to disk portions of slicememory buffers that may be needed shortly thereafter by the volumevisualization method increases, and can cause a continuouspage-in/page-out effect that dramatically decreases the computer'sprocessing performance. This problem is commonly known as “diskthrashing”.

For example, the Windows XP Virtual Memory Manager begins paging memoryto disk only when all the physical memory is used up (i.e. when there isno more memory available). Under such low memory conditions, allapplications become highly unresponsive because the operating system isbusy paging memory segments in and out of disk. Since each paged segmentis only 64 Kilobytes, it takes a long time to recover from low-memoryconditions.

Further, the Windows XP Virtual Memory Manager has no knowledge of whichimage data buffers are being actively used and which are not, andtherefore it tries to keep them all in memory until all the physicalmemory is saturated. When paging image data to disk, it has no knowledgeof whether that data will be soon needed again, and therefore it can behighly inefficient.

Another limitation is in the virtual memory addressing capability of32-bit CPUs, which address about 4.2 billion byte elements. In somevirtual memory addressing systems one of the 32 address bits is reservedfor kernel memory of the operating system, and therefore the remainingaddress space available for virtual memory allocation is reduced byhalf, that is about 2.1 billion byte elements. Thus, the size of thevirtual memory can be exceeded: for example, a three-dimensional volumeof seismic data with 2048 slice buffers each with 2048×2048 gridelements, would require over 8.5 billion byte elements of storage,exceeding the virtual memory addressing capabilities of a 32-bit CPU. Ifmultiple large volumes need to be allocated, the limited number ofvirtual memory addresses for slice buffers also becomes problematic.

As shown above, applications that process large data volumes aredifficult for computers to serve, due to the limited amounts of physicalmemory, limited virtual address space, and inefficiencies in theoperating system's virtual memory management and swap file.

Therefore, a need exists for an efficient memory management method forhandling large data volumes.

SUMMARY OF THE INVENTION

According to an embodiment of the present invention, a method ofmanaging a memory system for large data volumes comprises a centralmemory management system providing an interface between a plurality ofapplications and the physical memory of a programmed computer.

The method further comprises maintaining a global priority list ofmemory buffers allocated by a plurality of applications as alinked-list, wherein the list is sorted by when each buffer was lastaccessed by an application. The priority list maps data of the storagedevice to buffers of a virtual memory, wherein the buffers of thevirtual memory are paged-in to physical memory as they are requested bythe plurality of applications.

The method comprises specifying a low physical memory limit, andmonitoring the amount of usable physical memory, and upon determiningthat the usable physical memory falls below the low physical memorylimit, paging-out least-recently used slice buffers from the physicalmemory, through the memory management interface, increasing the usablephysical memory to about a specified high physical memory limit.

The method further comprises determining an unused data buffer in avirtual address space of the memory system coupled to the physicalmemory, marking the unused data buffer, and recovering a virtual addressspace by unmapping the unused data buffer from the virtual address spaceupon detecting that a programmed computer is allocating more virtualmemory than a computer processor can address.

The method further comprises sharing data buffers stored in the physicalmemory, through the memory management interface, among a plurality ofapplications, wherein the data buffers contain shared data, anddetermining the priority list of buffers accessed by the plurality ofapplications, wherein the priority list maps the data buffers to astorage device.

The method comprises identifying, uniquely, a given data bufferaccording to the contained shared data, wherein a creating applicationthat creates the given data buffer assigns an identifier, anddetermining whether the identifier has been previously assigned to ashared data buffer, and upon determining that the identifier alreadyexists in the physical memory, giving the creating application access tothe shared data buffer.

The method comprises addressing an object pointing to a data buffer in acentral memory management system directly with a memory address fromwithin an application using the central memory management system, andvalidating the memory address using a key, wherein the key comprisesunique information and is known to both a sender and a receiver of theobject. The method comprises providing a unique handle, combining thememory address and the handle in a fast-retrieval handle, sharing thefast-retrieval handle among two or more applications, and determiningwhether an object identified by the fast-retrieval handle is valid uponaccessing the object.

Maintaining the global priority list further comprises adding an objectto the global priority list corresponding to a data buffer upon creationof the data buffer, and removing the object from the global prioritylist upon determining the data buffer pointer corresponding to theobject has been deleted, wherein the object's parent object and childobject in the global priority list are linked prior to removing theobject. Maintaining the list further comprises moving the object to anend of the list upon determining that the object is to be used, whereinthe object at the end of the global priority list is less likely to beflushed than an object at a beginning of the global priority list. Themethod comprises notifying the plurality of applications of a bufferaddress change due to memory unmapping or mapping operations.

According to an embodiment of the present invention, a memory managementsystem comprises one or more storage devices for storing paging files, apriority linked-list coupled to the storage devices, wherein nodes ofthe priority linked-list are associated with the paging files of thestorage devices, and a virtual memory space comprising a plurality ofdata buffers, each data buffer coupled to a unique node of the prioritylinked-list.

According to an embodiment of the present invention, a memory managementsystem either interfaces with a plurality of applications directly, oris coupled to a central image processing server which in turn providesan interface between at least one application and the memory managementsystem.

BRIEF DESCRIPTION OF THE DRAWINGS

Preferred embodiments of the present invention will be described belowin more detail, with reference to the accompanying drawings:

FIG. 1 is a diagram showing typical use cases regarding memory usage ofan image processing application;

FIG. 2 is a diagram visualizing a relationship between physical, virtualand hard disk memory and its management through a priority linked-listin a memory management system according to an embodiment of the presentinvention;

FIG. 3 is a diagram of a system according to an embodiment of thepresent invention;

FIG. 4 is a diagram of a system implementing memory management accordingto an embodiment of the present invention;

FIG. 5 is an illustration of an application server architectureaccording to an embodiment of the present invention;

FIG. 6 is a diagram of a memory management system for a plurality ofapplications according to an embodiment of the present invention;

FIG. 7 is a diagram of a memory management system for a plurality ofapplications according to an embodiment of the present invention; and

FIG. 8 is a diagram of a fast-retrieval handle that combines objectaddress and system memory-mapping handle used in the embodiment of acentral service memory management system according to an embodiment ofthe present invention.

DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS

According to an embodiment of the present invention, computer memory isefficiently managed, wherein the memory is allocated for a data volume.A method of managing memory is disclosed by way of an example in termsof an imaging application for the storage and visualization oftwo-dimensional slices and three-dimensional volumes comprising suchslices. Referring to FIG. 2, a series of memory buffers 201 is allocatedfor each two-dimensional slice. The data contained in each memory buffercan be obtained, for example, from medical tomographic scanners such asMagnetic Resonance (MR), Computed Tomography (CT), Positron EmissionTomography (PET), or any other apparatus capable of producing a seriesof slices in a grid-like array. Each memory buffer or slice buffer hasits own virtual paging file, e.g., 202, which can be paged-in from orpaged-out to a storage device 203. The storage device can be, forexample, a magnetic hard-disk device. A memory manager 204 can createand access multiple virtual paging files on multiple storage devices,e.g., 205, maximizing the storage capacity of a programmed computerimplementing the memory manager 204.

According to an embodiment of the present invention, the effectiveperformance of an existing virtual memory paging system and magnetichard disk apparatus of the programmed computer is improved by utilizinga global linked-list 206 that keeps track of the most-recently used andthe least-recently used two-dimensional slice buffers 201. When theprogrammed computer accesses the data of a slice buffer, the memorymanager 204 determines whether a usable amount of Random Access Memory(RAM) 207 of the programmed computer has fallen below a predefined lowlimit. If so, a set of least-recently used memory buffers are paged-outto the storage device, e.g., a hard-disk device, until a predefinedamount of usable RAM is recovered. Thus, the computer memory isprevented from becoming overloaded, allowing the efficient visualizationof three-dimensional volumes comprising a very large number of slices.

Applications that manipulate large amounts of data can request moreresources from the programmed computer than is practical for efficientoperation. For example, image-processing applications exist that allow auser to create any desired number of Raster and Bitplane objects ofvarious sizes. A large number of these objects can quickly use up allthe available physical memory (e.g., RAM memory), forcing a virtualmemory manager, such as the Windows XP Virtual Memory Manager, tocontinuously swap memory segments to disk, greatly degrading a system'sperformance. According to an embodiment of the present invention,employing a memory management architecture for the allocation of memorybuffers prevents low-memory conditions and maintains a desirable levelof performance and interactivity. The memory management architecture canbe implemented with any object type. Object types can exhibit grouping,dependencies/relationships, notifications, or other high-levelfunctionalities.

It is to be understood that the present invention may be implemented invarious forms of hardware, software, firmware, special purposeprocessors, or a combination thereof. In one embodiment, the presentinvention may be implemented in software as an application programtangibly embodied on a program storage device. The application programmay be uploaded to, and executed by, a machine comprising any suitablearchitecture.

Referring to FIG. 3, according to an embodiment of the presentinvention, a computer system 301 for implementing the present inventioncan comprise, inter alia, a central processing unit (CPU) 302, a memory303, and an input/output (I/O) interface 304. The computer system 301 isgenerally coupled through the I/O interface 304 to a display 305 andvarious input devices 306 such as a mouse and keyboard. The supportcircuits can include circuits such as cache, power supplies, clockcircuits, and a communications bus. The memory 103 can include randomaccess memory (RAM), read only memory (ROM), disk drive, tape drive,etc., or a combination thereof. The present invention can be implementedas a routine 307 that is stored in memory 303 and executed by the CPU302 to process the signal from the signal source 308. As such, thecomputer system 301 is a general-purpose computer system that becomes aspecific purpose computer system when executing the routine 307 of thepresent invention.

The computer platform 301 also includes an operating system and microinstruction code. The various processes and functions described hereinmay either be part of the micro instruction code or part of theapplication program (or a combination thereof), which is executed viathe operating system. In addition, various other peripheral devices maybe connected to the computer platform such as an additional data storagedevice and a printing device.

It is to be further understood that, because some of the constituentsystem components and method steps depicted in the accompanying figuresmay be implemented in software, the actual connections between thesystem components (or the process steps) may differ depending upon themanner in which the present invention is programmed. Given the teachingsof the present invention provided herein, one of ordinary skill in therelated art will be able to contemplate these and similarimplementations or configurations of the present invention.

Referring to FIG. 4, a memory management system 401 can support multipleapplications (402, 404, 405) simultaneously. That is, the memorymanagement system 401 serves multiple instances of a memory library. Theapplications can interface directly with the memory management system401 and/or through another layer, such as a library server 403.

A method of managing a memory system comprises sharing data buffersstored in a physical memory among a plurality of applications, whereinthe data buffers contain shared data. The memory manager has knowledgeof all the shared data buffers stored in the physical memory. The methodcomprises identifying a given data buffer according to the containedshared data, wherein a creating application that creates the given databuffer assigns an identifier. The identifier is unique to the data ofthe data buffer; therefore, if two applications attempt to create a databuffer for the same data, the same identifier will be generated. Themethod comprises determining whether the identifier has been previouslyassigned to a shared data buffer, and upon determining that theidentifier already exists in the physical memory, giving the creatingapplication access to the shared data buffer.

According to an embodiment of the present invention, a MemoryMap objecttype and a MemoryManager object type are provided.

The MemoryMap object allocates memory using a memory-mapped buffer.Memory-mapped buffers can be used just like any other memory buffer, forexample allocated with malloc or new functions of the C-languageruntime, but in addition memory-mapped buffers offer other advantages.

Instead of being backed by the default operating system's swap file,each memory-mapped buffers is backed by a temporary paging file, whichcan be specified programmatically. This makes it possible to allocatemore memory than what could fit into a typical operating system swapfile. The MemoryMap objects also allow temporary files to be created ondifferent disks, wherein the total allocated memory can be as high asthe sum of all the free disk space available on multiple disks, e.g.,several Gigabytes.

A memory-mapped buffer can be shared between different processes and/orapplications. This is important to the transfer of data betweenprocesses in a client-server architecture, e.g., see FIG. 5, withouthaving to make additional copies of the data.

Unlike other memory buffers (for example, those that are allocated withmalloc or new), memory-mapped buffers according to an embodiment of thepresent invention can be flushed out of physical memoryprogrammatically.

Referring again to the imaging application example, when creating Rasteror Bitplane objects, internally the image data is stored in an instanceof the MemoryMap object type, which allocates a memory-mapped imagebuffer. A set of Configuration Parameters (for example, provided by anoperating system) allow the specification of parameters such as how manydisks should be used for memory-mapping, how much space can be used oneach disk, and the pathname where the temporary paging files should becreated.

An instance of the MemoryManager object is responsible for monitoringthe available free physical memory, and for flushing least recently usedmemory-mapped buffers to disk when approaching low-memory conditions.Thus, the MemoryManager object can keep track of which image buffers areactively being used and which image buffers have not being usedrecently. By using the knowledge of the active and/or inactive buffers,the MemoryManager object can be selective about which buffers should beflushed to disk, providing greater paging efficiency than can beachieved using, for example, the Windows NT virtual memory manager.

The MemoryManager object can page an entire memory-mapped image bufferto disk at once, providing additional free physical memory.

The MemoryManager object can continue flushing until a desired memorysize, e.g., several Megabytes, have been paged to disk. Therefore, theperiod between low-memory conditions can be increased.

The MemoryManager object can flush memory-mapped buffers out of physicalmemory before all memory is saturated, maintaining sufficient memorysuch that applications have a desirable response time.

A set of configuration parameters allow for the specification of aminimum amount of free physical memory before buffers are flushed, andan amount of physical memory to be recovered upon flushing the buffers.

Referring to FIG. 5, the MemoryManager object 501 comprises alinked-list 502 of all the MemoryMap objects, 503 and 504, created bythe client image processing application(s). The linked-list 502 ismaintained in a sorted order, so that the least recently used bufferscan always be found at the beginning of the list (e.g., items thatshould be flushed first), while the most recently used buffers are foundat the end of the list (e.g., items that should be flushed last).

Methods for keeping linked-lists in sorted order are highly efficient,and need little overhead. The linked-list does not need to bere-arranged by a sorting operation, the only operations involved areappending or moving items at the end of the list. The linked-list ismaintained sorted by implementing the following procedures:

-   -   Whenever an image buffer is created, a newly allocated MemoryMap        object adds itself to the end of the list, since it is more        likely to be used soon.    -   Whenever an image buffer pointer is deleted, its corresponding        MemoryMap object removes itself from the list, joining its        parent link with its child link. Therefore the list does not        need to be traversed when deleting an item.    -   Whenever an image buffer is about to be used, its corresponding        MemoryMap object is moved to the end of the list, so that it is        less likely to be flushed. Then the total free physical memory        is checked, and if it falls below a certain threshold the first        item in the list is flushed to disk, and moved at the end of the        linked-list as well.

These procedures are sufficient to guarantee that actively used imagebuffers, as well as buffers which have just been flushed, are at the endof the list. The remaining items at the beginning of the list are alwaysthe least recently used buffers. It should be understood that othermethods of maintaining a linked-list are contemplated, and that one ofordinary skill in the art would appreciate that these others methods canbe implemented. For example, a most-frequently used linked-list.

The MemoryMap object allows the application to lock a buffer while it isaccessed. This information is stored in a flag corresponding to thebuffer accessible to the MemoryManager object. Therefore, theMemoryManager knows which buffers are currently used by the imageprocessing application according to the flags. Using a flag thatindicates if a buffer is used, the MemoryManager object can un-mapcurrently unused memory-mapped buffers to reduce the footprint on theapplication's virtual address space. This optimization takes place whena new buffer is requested that does not fit into the available virtualaddress space of the image processing application, is transparent to theapplication itself and allows addressing of more data than nativelysupported by the processors architecture, for example, 2 Gigabytes.

When the MemoryManager object un-maps a buffer from the virtual addressspace of the application and maps it back later when the buffer isaccessed again the address within the virtual address space may bedifferent from the initially assigned address when the buffer wascreated. For this reason, an application needs to be programmed not tomaintain memory-mapped buffer addresses past the lifetime of acorresponding object, as they can become invalid. However, according toan embodiment of the present invention, any application usingmemory-mapped buffers through a MemoryMap object can be notifiedwhenever a buffer's address has been changed due to mapping operations,so that the application can maintain up to date data addresses.

The Memory Management embodiment described previously is also applicableto parallel running image processing applications as shown in FIGS. 6and 7. Parallel running applications use a central instance of theMemoryManager object 401 that manages a linked-list of all memory-mappedbuffers for all applications. The decision about which buffers to flushto optimize the available physical memory is done based on this globallist. Once the oldest buffers have been selected to be flushed out ofphysical memory, all applications holding a reference to those buffersare notified. Thus, the flushing command needs to be issued by allapplications that share this buffer.

Exchanging address references of the MemoryMap object instances betweenthe centralized Memory Management and the applications is needed toallow direct access without additional list traversals or lookups.However, accessing these addresses directly carries the risk of accessviolations in case where an object instance is destroyed in themeantime. An embodiment of the Memory Management for parallel imageprocessing applications can combine the MemoryMap object address 801with a system memory-mapping handle 802 to validate the integrity of thememory address 801 as shown in FIG. 8. Once the retrieval handle 803 isreceived by the application, the address pointer 801 is only validatedif the attached system memory-mapping handle 802 can be found at thegiven address as well.

While addressing remote objects indirectly via identifiers causesadditional overhead in managing the list of identifiers and specificallyin traversing it each time an objects needs to be addressed, theadditional overhead can be reduced or eliminated by addressing an objectdirectly with its memory address across applications and validating thememory address using a key. The key provides additional information thatvaries from object to object and is known to both sender and receiver.On a remote side the object's key needs to be stored within the remoteobject's memory address, for example, as a class member variable orfield in object oriented programming languages. When an object isdeleted this key is overridden with a default value, for example, usingthe class destructor in object oriented programming languages. Combiningthe object's memory address 801 with the key 802 into a single unit orretrieval-handle 803 allows for direct addressing of remote objectsacross logical or physical boundaries in a safe fashion. Beforeaccessing the memory address that is stored within the retrieval-handle803, the remote side determines whether the key 802 from theretrieval-handle 803 can also be found at the given memory address 801.This is only the case for objects whose lifetime did not yet expire.

The key 802 can be any sufficiently unique alphanumeric value, forexample, sequential numbers, randomly generated numbers or resourcehandles of system resources associated with an object.

Having described embodiments for a virtual memory system and method forhandling large data volumes, it is noted that modifications andvariations can be made by persons skilled in the art in light of theabove teachings. It is therefore to be understood that changes may bemade in the particular embodiments of the invention disclosed which arewithin the scope and spirit of the invention as defined by the appendedclaims. Having thus described the invention with the details andparticularity required by the patent laws, what is claimed and desiredprotected by Letters Patent is set forth in the appended claims.

1. A method of managing a memory system for large data volumescomprising providing a central memory management system comprising amemory management interface between a plurality of applications and aphysical memory of a programmed computer.
 2. The method of claim 1,further comprising maintaining a global priority list of data buffersallocated by the plurality of applications as a linked-list, wherein thelist is sorted according to an order in which data buffers are accessedby the plurality of applications.
 3. The method of claim 2, wherein theglobal priority list maps data of a storage device to data buffers of avirtual memory, wherein the data buffers of the virtual memory arepaged-in to physical memory as they are requested by the plurality ofapplications.
 4. The method of claim 1, further comprising: specifying alow physical memory limit; and monitoring an amount of usable physicalmemory, and upon determining that the usable physical memory falls belowthe low physical memory limit, paging-out least-recently used memorybuffers from the physical memory, through the memory managementinterface, increasing the usable physical memory to about a specifiedhigh physical memory limit.
 5. The method of claim 1, furthercomprising: determining an unused data buffer in a virtual address spaceof the memory system coupled to the physical memory; marking the unuseddata buffer; and recovering a virtual address space by unmapping theunused data buffer from the virtual address space upon detecting thatthe programmed computer is allocating more virtual memory than acomputer processor can address.
 6. The method of claim 1, furthercomprising: sharing data buffers stored in the physical memory, throughthe memory management interface, among the plurality of applications,wherein the data buffers contain shared data; and determining a prioritylist of buffers accessed by the plurality of applications, wherein thepriority list maps the data buffers to a storage device.
 7. The methodof claim 1, further comprising: identifying, uniquely, a given databuffer according to contained shared data therein, wherein a creatingapplication that creates the given data buffer assigns an identifier;and determining whether the identifier has been previously assigned to ashared data buffer, and upon determining that the identifier alreadyexists in the physical memory, giving the creating application access tothe shared data buffer.
 8. The method of claim 1, further comprising:addressing an object pointing to a data buffer in the central memorymanagement system directly with a memory address from within anapplication using the central memory management system; and validatingthe memory address using a key, wherein the key comprises uniqueinformation and is known to both a sender and a receiver of the object.9. The method of claim 8, further comprising: providing a unique handle;combining the memory address and the handle in a fast-retrieval handle;sharing the fast-retrieval handle among two or more applications; anddetermining whether an object identified by the fast-retrieval handle isvalid upon accessing the object.
 10. The method of claim 2, whereinmaintaining the global priority list further comprises: adding an objectto the global priority list corresponding to a data buffer upon creationof the data buffer; removing the object from the global priority listupon determining the data buffer pointer corresponding to the object hasbeen deleted, wherein the object's parent object and child object in theglobal priority list are linked prior to removing the object; and movingthe object to an end of the list upon determining that the object is tobe used, wherein the object at the end of the global priority list isless likely to be flushed than an object at a beginning of the globalpriority list.
 11. The method of claim 5, further comprising notifyingthe plurality of applications of a buffer address change due to memoryunmapping or mapping operations.
 12. A memory management systemcomprising: a storage device for storing paging files; a prioritylinked-list coupled to the storage device, wherein nodes of the prioritylinked-list are associated with the paging files of the storage devices;and a virtual memory space comprising a plurality of data buffers, eachdata buffer coupled to a unique node of the priority linked-list. 13.The system of claim 12, comprising two or more storage devices.
 14. Thesystem of claim 12, wherein a memory management system is coupled to acentral image processing server providing an interface between at leastone application and the memory management system.
 15. A program storagedevice readable by machine, tangibly embodying a program of instructionsexecutable by the machine to perform method steps for managing a memorysystem for large data volumes, the method steps comprising: providing acentral memory management system comprising a memory managementinterface between a plurality of applications and a physical memory of aprogrammed computer.
 16. The method of claim 15, further comprisingmaintaining a global priority list of data buffers allocated by theplurality of applications as a linked-list, wherein the list is sortedaccording to an order in which data buffers are accessed by theplurality of applications.
 17. The method of claim 16, wherein theglobal priority list maps data of a storage device to data buffers of avirtual memory, wherein the data buffers of the virtual memory arepaged-in to physical memory as they are requested by the plurality ofapplications.
 18. The method of claim 15, further comprising: specifyinga low physical memory limit; and monitoring an amount of usable physicalmemory, and upon determining that the usable physical memory falls belowthe low physical memory limit, paging-out least-recently used memorybuffers from the physical memory, through the memory managementinterface, increasing the usable physical memory to about a specifiedhigh physical memory limit.
 19. The method of claim 15, furthercomprising: determining an unused data buffer in a virtual address spaceof the memory system coupled to the physical memory; marking the unuseddata buffer; and recovering a virtual address space by unmapping theunused data buffer from the virtual address space upon detecting thatthe programmed computer is allocating more virtual memory than acomputer processor can address.
 20. The method of claim 15, furthercomprising: sharing data buffers stored in the physical memory, throughthe memory management interface, among the plurality of applications,wherein the data buffers contain shared data; and determining a prioritylist of buffers accessed by the plurality of applications, wherein thepriority list maps the data buffers to a storage device.
 21. The methodof claim 15, further comprising: identifying, uniquely, a given databuffer according to contained shared data therein, wherein a creatingapplication that creates the given data buffer assigns an identifier;and determining whether the identifier has been previously assigned to ashared data buffer, and upon determining that the identifier alreadyexists in the physical memory, giving the creating application access tothe shared data buffer.
 22. The method of claim 15, further comprising:addressing an object pointing to a data buffer in the central memorymanagement system directly with a memory address from within anapplication using the central memory management system; and validatingthe memory address using a key, wherein the key comprises uniqueinformation and is known to both a sender and a receiver of the object.23. The method of claim 16, wherein maintaining the global priority listfurther comprises: adding an object to the global priority listcorresponding to a data buffer upon creation of the data buffer;removing the object from the global priority list upon determining thedata buffer pointer corresponding to the object has been deleted,wherein the object's parent object and child object in the globalpriority list are linked prior to removing the object; and moving theobject to an end of the list upon determining that the object is to beused, wherein the object at the end of the global priority list is lesslikely to be flushed than an object at a beginning of the globalpriority list.
 24. The method of claim 19, further comprising notifyingthe plurality of applications of a buffer address change due to memoryunmapping or mapping operations.